A 400 HTTP response does not replace the Server entry header as it does it for a 200 response when using a rule like:
Type of rule: HTTP response headers
Incoming URL pattern: *
HTTP response codes: 200,400
Expires header: X Dont add header
Custom Header: Name: Server Value: "what ever" X Override
Using telnet with:
Get / HTTP/1.1
host: 10.0.0.4
returns:
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2003 07:49:01 GMT
Last-Modified: Sat, 14 Jun 2003 10:48:51 GMT
Content-Type: text/html; charset=US-ASCII
Content-Length: 860
Cache-control: private
ETag: W/"MTAtODA4NS1DMTI1NkQ0NTAwM0I2NzI1LTAtMA=="
Server: what ever
Using telnet with:
Get /
returns:
HTTP/1.1 400 Bad Request
Server: Lotus-Domino
Date: Fri, 20 Jun 2003 07:50:11 GMT
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Expires: Fri, 20 Jun 2003 07:50:11 GMT
Content-Type: text/html
Content-Length: 161
<HTML><HEAD><TITLE>Unable to Process Request</TITLE></HEAD><BODY><P>Http Status Code: 400</P><P>Reason: Unknown or unsupported protocol version</P></BODY></HTML>
The server entry is not replaced
Return to top
Print this page
